home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 19
/
Night Owl (The Best of Shareware)(NOPV 19)(1996).ISO
/
018a
/
elrul512.zip
/
4DOS_TC.RUL
< prev
next >
Wrap
Text File
|
1995-07-17
|
8KB
|
168 lines
4DOS_TC USERS GUIDELINES
4DOS_TC - The 4DOS/4OS2 and Take Command Support Conference/Echo.
Moderators - Raymond Beriau, 1:242/105@FidoNet.Org
Phi Nguyen, 1:379/10@FidoNet.Org
Description - Technical support and file exchanges for both 4DOS (command
processor for DOS) and 4OS2 (command processor for OS2) and
Take Command (command processor for Windows).
*** ALL MESSAGES MUST BE POSTED/WRITTEN IN ENGLISH! English is the ONLY
official language allowed here. ***
1 - This conference/echo is for 4DOS/4OS2/TC SUPPORT. This means that
messages posted in here should pertain to 4DOS/4OS2/TC and related
utilities such as BTM files as well as REXX scripts.
2 - Please leave moderating to the moderators (Raymond Beriau and/or
Phy Nguyen). DO NOT reply to off-topic messages!
3 - All are welcome. All participants in this conference are expected to
behave as adults. No insults to anyone will be tolerated. Also, a
close eye will be kept on any systems/BBSs to see that debates do not
turn into senseless arguments. If you want to start one, do not start
it in 4DOS_TC!
4 - Rules of Common Courtesy apply at ALL times. While we have no
objections to a little bit of debate (as long as it is relevant to
4DOS/4OS2/TC), it should be kept at a polite level and not escalate
into a flame war.
5 - Real names should be used at all times. If your system/BBS uses only
aliases/nicknames, then all messages MUST be signed with your real
name.
6 - Leave politics and religions at the door. Discussions about things
not related to 4DOS/4OS2/TC/REXX do not belong here.
7 - As stated in the EchoMail Policies, no messages containing illegal
information or activities are allowed. For those who do not know,
these includes long distance phone codes, credit cards numbers, etc..
8 - A SYStem OPerator is responsible for all messages that originate from
his/her system/BBS.
9 - When someone posts a message requesting help, please try to be as
helpful and accurate as possible. Blatant "Rear The Fine Manual"
messages will not be tolerated. Screaming "RTFM" leaves the person as
confused as they were before and adds yet another useless message to
this echo. Pointing out page numbers and/or sections in the docs for
more information is acceptable.
10 - Avoid creating unneeded traffic. Many people pay long distance
charges to receive this conference. Specifically:
a) Frivolous items such as BBS ads, 'test' messages, "Where are you
from" chains, multiple tearlines, replies to off-topic messages,
large signatures and so forth, are not to be posted in this
conference. Encrypted messages, PGP signatures, etc, should be not
used in this conference. If you feel the need for secrecy, use
direct NetMail, or better yet, use the telephone. :-)
b) Even though it may seem polite to do so, please refrain from posting
messages that say nothing more than 'Thank you'. Instead, answer
someone else's question(s) when you can and pass along the help that
was once given to you. Your thanks may be posted 'in advance' when
you ask your question, but it is usually assumed.
c) Please refrain from correcting someone spelling or grammar as not
everybody has perfect spelling. While most people have spell
checkers, quite a few including myself don't have a grammar checker.
d) Please, keep the quoted portion of your message SHORT! The people
that use this conference are not so feeble minded that they need an
entire message quoted back to them. Quote just enough to let one know
what you are replying to, just enough to identify the thread of the
conversation for other users. DO NOT quote BBS addresses, kludge lines
and previous tagline, braglines, Origin lines, tearlines, signatures,
etc. - there is no need for them.
e) Ads for any utilities may be posted (within reason) and discussed
here, as long as they pertain to 4DOS/4OS2/TC and/or utilities.
f) Questions about when future versions of 4DOS/4OS2/TC will be released
are considered off-topic. Announcements regarding the status of
upcoming versions of will be made from time to time, as appropriate.
g) Discussions about the "superiority" of various Operating Systems are
not allowed. How 4DOS/4OS2/TC operates under various operating
systems may be discussed on a factual and polite level (without
putting down other operating systems such as Microsoft DOS and
Windows).
h) No automatic file announcements are allowed, unless done via the
moderators. You may, however, help others find programs. When doing
so, do not just say "I have it"... Include the complete filename
under which the file(s) can be requested, and what (if any)
restrictions you have on file requests. (We are not mind readers
here...). In the case of files via ftp, *try* to include the site
AND directory location of the file as well.
11 - HIGH BIT ASCII GRAPHIC CHARACTERS are not permitted in this
conference. High-bit pictures, signatures, boxed quotes and other
pointless uses of high-bit ASCII are not allowed. (Signatures, if you
must, should be no more than a line, or two at the most.)
12 - Posting of encoded files is permitted (NOT encrypted file):
a) As long as the file is first archived/compressed (if longer than a
few kilobytes) using LHA (other software such as ARC, ARJ, PAK, RAR,
UC2, ZIP can be used as long as the archiver type is mentioned, but
LHA/LZH is the preferred one).
b) As long as encoders such as Chad Wagner's XXBUG or Horst Schaeffer's
CSCRIPT are used - UUencode is not acceptable.
13 - BTM suggestions - when posting a file in 4DOS_TC:
a) BTM files should never be compressed - please, do not use BATCOMP.EXE
nor any other compressors. BTM files should be kept in their
original 4DOS BAT/BTM format.
b) Do not rely on your 4DOS setup when creating a BTM file - test the
file on a pure/vanilla 4DOS system.
c) Start your BTM file with the following 4DOS command:
@ECHO OFF
SETLOCAL
UNSET *
UNALIAS *
d) Follow up by setting the variables as well as any aliases and paths
that are pertinent to the BTM file - although requiring more space,
it is a good programming habit to identify each of the variables as
well as their use, each of the aliases as well as their purpose, and
each of the temporary directories as well as their purpose.
e) Finish your BTM file with the ENDLOCAL command to restore thing the
way they were before starting the BTM file.
14 - Posting of encoded files is permitted (NOT encrypted file):
a) As long as the file is first archived/compressed (if longer than a
few kilobytes) using LHA (other software such as ARC, ARJ, PAK, RAR,
UC2, ZIP can be used as long as the archiver type is mentioned, but
LHA/LZH is the preferred one).
b) As long as encoders such as Chad Wagner's XXBUG or Horst Schaeffer's
CSCRIPT are used - UUencode is not acceptable.
15 - XXencoding suggestions - when posting a file in 4DOS_TC:
a) First archive/compress your BTM file with LHA (latest version release
is 2.13) - LHA/LZH is preferred archiver/compressor for 4DOS_TC.
b) When creating XXencoded scripts, limit the number of line to a
maximum of 90 per message using the following XXBUG option:
XXBUG /MP=90
4DOS_TC Users Guidelines - Originally Written March 01, 1995
Last revised May 26, 1995
---